Skip to content

fix(incoming-task): fix-incoming-task-overflow-issue#482

Merged
mkesavan13 merged 5 commits into
webex:ccwidgetsfrom
akulakum:IC_TASK_OVERRIDE_STYLE_ISSUE
Jul 3, 2025
Merged

fix(incoming-task): fix-incoming-task-overflow-issue#482
mkesavan13 merged 5 commits into
webex:ccwidgetsfrom
akulakum:IC_TASK_OVERRIDE_STYLE_ISSUE

Conversation

@akulakum

@akulakum akulakum commented Jun 30, 2025

Copy link
Copy Markdown
Contributor

COMPLETES #https://jira-eng-sjc12.cisco.com/jira/browse/CAI-6598

Vidcast link: https://app.vidcast.io/share/fd9dc8bf-91ac-4b30-8fc1-0e744ac552c3

This pull request addresses

This pull request addresses the issue of overflowing content in multiple widgets when handling long email addresses as the media type. Specifically:

1. Context of the Issue:

  • In the Incoming Task Widget rendered in toast notifications, when the media type is email and the user's email address is long, the following problems occur:
  1. The email icon overflows outside of the container.
  2. The email text does not wrap or display an ellipsis, causing layout issues.
  • This issue is not limited to the Incoming Task Widget but is also present in the Call Control Widget and the Task List Widget.

2. Fixes Provided:

  • The overflow issue has been resolved in the Incoming Task Widget, ensuring:
  1. The email icon stays within the container.
  2. Long text is properly truncated using ellipsis.
  3. A tooltip is shown for digital tasks (e.g., email, chat) to view the full content.
  4. No tooltip is shown for voice-related tasks.
  • Similar fixes have been implemented in the Call Control Widget and Task List Widget to maintain consistency and resolve the same issue across all affected components.

by making the following changes

< DESCRIBE YOUR CHANGES >

Screenshot 2025-07-02 at 9 16 00 PM Screenshot 2025-07-02 at 9 14 32 PM

Change Type

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Tooling change
  • Internal code refactor

The following scenarios were tested

  • The testing is done with the amplify link
    < ENUMERATE TESTS PERFORMED, WHETHER MANUAL OR AUTOMATED >

The GAI Coding Policy And Copyright Annotation Best Practices

  • GAI was not used (or, no additional notation is required)
  • Code was generated entirely by GAI
  • GAI was used to create a draft that was subsequently customized or modified
  • Coder created a draft manually that was non-substantively modified by GAI (e.g., refactoring was performed by GAI on manually written code)
  • Tool used for AI assistance (GitHub Copilot / Other - specify)
    • Github Copilot
    • Other - Please Specify
  • This PR is related to
    • Feature
    • Defect fix
    • Tech Debt
    • Automation

Checklist before merging

  • I have not skipped any automated checks
  • All existing and new tests passed
  • I have updated the testing document

@coderabbitai

coderabbitai Bot commented Jun 30, 2025

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@aws-amplify-us-east-2

Copy link
Copy Markdown

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-482.d1b38q61t1z947.amplifyapp.com

@adhmenon adhmenon added validated Indicates that the PR is ready for actions run_e2e Add this label to run E2E test for meeting and CC widgets labels Jun 30, 2025

@mkesavan13 mkesavan13 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's run this through UX to know if we should word wrap or add ellipsis and a tooltip everywhere


.customer-name::part(text),
.phone-number::part(text) {
white-space: normal !important;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we not have the !important tag instead increase the CSS Specificity?

@mkesavan13 mkesavan13 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Thanks, Akula :-)

@adhmenon adhmenon left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall LGTM. Just one question about the custom stles

color: var(--mds-color-theme-indicator-secure);
}
}
.call-control-task-tooltip::part(popover-content) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious - we are using custom styles here - UX is alright with the changes correct?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we are overriding the Momentum default styles here to enable text wrapping for the tooltip. UX has reviewed and is okay with these custom style changes.

@mkesavan13
mkesavan13 merged commit af70bee into webex:ccwidgets Jul 3, 2025
8 of 9 checks passed
github-actions Bot pushed a commit that referenced this pull request Jul 3, 2025
# [1.28.0-ccwidgets.84](v1.28.0-ccwidgets.83...v1.28.0-ccwidgets.84) (2025-07-03)

### Bug Fixes

* **incoming-task:** fix-incoming-task-overflow-issue ([#482](#482)) ([af70bee](af70bee))
@sreenara

sreenara commented Jul 3, 2025

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 1.28.0-ccwidgets.84 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

released on @ccwidgets run_e2e Add this label to run E2E test for meeting and CC widgets validated Indicates that the PR is ready for actions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants